Repository navigation
release: 0.1.1 — security floors and lock bumps (mint >= 1.10.2, plug_crypto 2.2.1, jose 1.11.13, cowlib 2.21.0) - #1
Merged
Conversation
plug_crypto 2.2.0 is affected by EEF-CVE-2026-105963 (fixed in 2.2.1). It is a transitive dev/test-only dependency here (via ueberauth -> plug), so only the mix.lock entry changes; the published package has no plug_crypto dependency and needs no release. Ref: ghostex-547
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The full 0.1.1 security release — merge this, then push the
v0.1.1tag and the release workflow publishes to hex.pm.Security
mint >= 1.10.2— mint reaches every consumer transitively (req → finch → mint, all non-optional) and the published tarball ships nomix.lock, so the constraint must ride the package metadata. The floor clears all six open mint advisories (EEF-CVE-2026-82728/-82729 HIGH, -82672, -91043 HIGH, -92103, -94194) and keeps consumers off affected 1.9.3/1.10.0/1.10.1. Verified viamix hex.build: the published requirements now includemint >= 1.10.2 (app: mint).jose→ 1.11.13 (lock) — clears 8 advisories EEF-CVE-2026-65625…-65632 incl. HIGH -65629 (fixed release landed today).plug_crypto→ 2.2.1 (lock) — EEF-CVE-2026-105963 (MEDIUM).cowlib→ 2.21.0 (lock) — clears -43971/-43969; the unfixable -43966 remains, documented as accepted in AGENTS.md (no patched release exists; test-stack-only, off the runtime path).Release prep:
@version→ 0.1.1; CHANGELOG gains the 0.1.1 section (Keep-a-Changelog); the accepted-advisory note refreshed.Gates (verbatim):
mix precommitgreen — 45 passed, 0 skipped; credo strict clean (128 mods/funs);--warnings-as-errorsclean;mix hex.auditreports ONLY the accepted cowlib -43966 (exit 1 is that advisory alone);hex.buildrequirements evidence recorded.After merge:
git tag v0.1.1 && git push origin v0.1.1→.github/workflows/release.ymlcompiles, tests, and runsmix hex.publish --yes.Ref: ghostex-10a (and ghostex-545 for the investigation).